New Relic

New Relic helped us identify RDS lock wait timeouts for a clients high load e-commerce store. With the help of New Relic Application Performance Monitoring we were able to pin point the root cause and made changes to the table configurations of DB which helped us solve the degraded site performance.

We use New Relic for backend, frontend and synthetics observability. We need to know when our website for the users is performing.

After GA4 retired the page speed reports, we installed New Relic on our site to make sure we didn't lose visibility into page load times. We quickly realized that it has a lot more capabilities than we were using or would ever use. It's a very powerful tool, but more for technical users.

NR is used as a monitoring and optimisation tool at our organisation. It integrates with several of our key other services such as AWS and helps development and support teams keep on top of their applications through the monitoring options and alerting / notification features. Lots of great visualisation options and customisation abilities to make it fit exactly what you do at your company. It helps us reduce MTTR and often catch issues before they become incidents which is very valuable for a company like ours when any amount of downtime can have a big knock on effect to our customers.

New Relic is used as a full-stack monitoring tool. It is used by various application teams within our organization for monitoring their application, server infrastructure, end-user, and synthetics. We have also started to leverage it for monitoring other cloud entities like lambda, RDS, etc along with Kubernetes clusters. It helps with monitoring and alerting mechanics and helps various notification methods.

we are using many new relic sub products for our many use cases we are using it as APM tools, infrastructure monitoring tool in order to monitor our large number of server fleet, Database monitoring, Kubernetes Cluster monitoring, track bugs and issues in application code, alerts and warnings for uptime of our application or to get the overall idea on how our product is performing under certain circumstances and for better scaling and resources optimisations.

New Relic is tightly integrated into our SDLC process and giving us feedback in not only how our application is performing, but how it is being used by our customers. Starting with onboarding our engineers can see how our application functions through our API calls, what services are used and how a request spans multiple services (both internally and externally). We can then use it in the application development phase in our lower level environments. Allowing engineers and QA easily identify errors or performance issues before it ever reaches our Production environment. Then finally in the Production environment, New Relic gives you an X-Ray machine into your application performance and monitoring. Understanding your transactions, where a bottleneck might lay within a specific API call because of a database call, or external call. The tool is used in every cycle of our SDLC for every engineer in our company. It is then heavily used by our SRE team for alerting and monitoring too.

We use New Relic for a wide range of monitoring and observability needs. We don't just gather system metrics, but also performance metrics and customer experience data from many different applications. Our ability to reference data collected from any number of systems has proven to be an invaluable troubleshooting tool. It also helps us with plotting growth, and planning for future capacity.

We use New Relic to get stats on page hits and performance metrics of our website, hosted on Acquia. We use it to monitor slow SQL queries and also page load times and get statistics on browser types as well as what device is accessing our site's pages. It is also the default performance monitoring tool for Acquia sites.

It is used across the whole organization. We use APM to monitor customers' applications, Infrastructure to review the infrastructure behaviors, Synthetics to check the availability of the customer's sites, and logs to review in a friendly way all those logs that are recorded from the app/infra. New Relic has become something basic in my day-to-day.

New Relic is being used by the University of South Australia (UniSA) Information Technology Unit to provide detailed insight into the end-user performance, availability, and error rate of the University's applications. The Unit supports critical systems that serve over 32,000 students.

Our solution hosts thousands of PHP applications in AWS cloud across multiple regions. We installed the PHP NewRelic agent and we set up each application to use a different newrelic_set_appname among with several newrelic_add_custom_parameter, like the database identifier where the site is in, the Autoscaling group where the site is running on, etc., that way we could identify which clients had the most traffic in a specific database server or Autoscaling group. To do that, we used Dashboards with queries to retrieve that data. NewRelic APM helped us a lot to identify why a site was slow when loading in the browser or when processing a specific php script. With Transactions and Databases features, we could even identify which specific php function of the code was stuck or which specific database query was taking too long. With External Services, we could detect when there was a delay connecting, for example, to Microsoft auth, Google auth, or even to another AWS service. In general, for us, it was a great tool to troubleshoot application slowness issues.

• Infrastructure Monitoring and Alerting
• Application Performance Monitoring and Alerting
• Tracking business and product related KPI's and metrics.
• Dashboards for NOC and the customer facing teams.

New Relic is the de-facto KPI tracking and dash-boarding tool for us. Apart from the APM - which is the USP of New Relic - even the technical and product KPIs are plotted on New Relic. It is used the tool for handshake and exchange of data between the various groups within the organisation.

New Relic is being used in our Organization for monitoring everything literally. All our devices & instances, whether they are present in AWS, GCP, or On-premises, are being monitored in New relic. New Relic has helped in making sure that all aspects of an instance are being monitored, and whenever something goes wrong, New Relic sends out an alert over email or any chosen platform.

We have used New Relic for application performance monitoring. Our product being B2C, we need to monitor the performance 24 * 7 for the best experience for our customers. At the same time, when a customer faces any issue, our Technology team requires all the necessary details to assess, debug and identify the root cause. New Relic has assisted in both the ways to proactively monitor and provide finer details to assist during an issue as well.

New Relic is primarily used for Application Performance Monitoring (APM) and Synthetic Monitoring. Their APM offering gives key insights into the health and performance of the company's web infrastructure. It is used to identify code bottlenecks, timeouts, and any requests or issues that are placing a heavy burden on the server. Additionally, it can be used to identify endpoints or requests that are causing poor customer experiences due to being slow or erroring. Synthetic Monitoring is used to evaluate whether certain functional features are working.

Monitoring ecommerce applications and performance thereof.

We use New Relic within the R&D department, but our support group uses it as well. We use it mainly for logging purposes (of our servers), but we also use it for monitoring our services and [sending] automatic alerts to ourselves based on these logs (meaning - when crossing a certain threshold of high error rates for example).

We use New Relic to set up dashboards to track errors, throughput, and performance. We also set up synthetic monitors and alarms to make sure our site pages are up and running.

I use New Relic in order to monitor and follow KPI about our application. Particularly, this allows us to detect performance issues.

We use New Relic on a daily basis to monitor software application performance and server utilization. We performance test a wide range of software and need to actively monitor and assess system capacity and address any issues found. New Relic provides the capacity for us to monitor the applications live or view historical data.

The most important use of New Relic for us is API monitoring. With NewRelic we have a real-time update about the APIS health, so we have configured alerts that trigger messages in google chat when some API is not running well. Also, it helps a lot in problems investigations, providing a lot of data to understand what is going on. We have minimal use in frontend applications too, to monitor the performance of our SPA.

New Relic is used across many departments in our company. Some of the areas we use New Relic for: - monitoring our API health and performance for our Prem and cloud applications. - tracking our Core web vitals. - Debug production issues (JS Errors, Stack traces, and profiling) - use synthetic scripts to monitor critical user flows.

New Relic is used across engineering departments to monitor how systems operate in both non-prod and production environments. For the component that I own, I use it to monitor Tomcat health (like the number of thread pools) and monitor the latency/error rate of the requests that my service handles. This helps us to understand how our system behaves, how much our system can handle, and help in capacity planning. I also set up important alert signals based on New Relic data and route the signal to Pager Duty that we have engineers on a routine schedule to pick up those alerts when something unexpected happened in production. This helps to quickly mitigate production issues that can surface to end-users

New Relic is used across my business unit and it is used for monitoring Infra, synthetics, dashboard, and alerting in case of any anomalies with the application.